Should integrity constraints be global or local?

Data base integrity constraints are commonly expressed as predicates over data base states or state changes (global constraints) or as preconditions of transactions that are to change data base states (local constraints). We argue that business reengineering, and the lack of sophistication of users favor local constraints, but that global constraints may also be necessary. Local constraints are expressed as preconditions of transactions in our specification language SF. Primarily to foster discussion, we extend the concept of integrity by introducing completeness and robustness as two new integrity classes, and define a number of additional discussion topics.